EnigmA Amiga Run 1997 July/EnigmA AMIGA RUN 20 (1997)(G.R. Edizioni)(IT)[!][issue 1997-07 & 08][EAR-CD IV].iso/lightwave/lwmlist/95.lightwave-08/000211_owner-lightwav…bcom.webcom.com_Mon Aug 14 20:12:02 1995.msg

Internet Message Format | 1995-09-02 | 3KB

Received: by webcom.webcom.com
    (1.37.109.15/16.2) id AA089946321; Mon, 14 Aug 1995 20:12:02 -0700
Return-Path: <[e-mail]>
Received: from minnie.risd.edu by webcom.webcom.com with SMTP
    (1.37.109.15/16.2) id AA089596292; Mon, 14 Aug 1995 20:11:33 -0700
Received: by minnie.risd.edu; id AA25695; Mon, 14 Aug 1995 23:04:12 -0400
Date: Mon, 14 Aug 1995 23:04:12 -0400 (EDT)
From: Joe Angell <[e-mail]>
Subject: Plug In idea..
To: [e-mail]
Cc: LightWave Mailing List <[e-mail]>
Message-Id: <[e-mail]>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: [e-mail]
Precedence: bulk

    While reading the new 3d studio Max info I got an idea for a great
plug in. The new 3ds alows you to go back and edit a model at any point
in it's creation. 3ds saves a stack file of every modification done to
the object so it can build it back up, with changes at any stage. I
thought this was a really great idea, and it could be implimented as a
plug in for modeler if we  can do one thing. We need to be able to extract
the numeric information from each edit, and info on which layer is active
etc. But we also need to be able to trigger the plug in after every
modeler command, so it knows to record the last command. Then the stack
of commands could be re-executed by modeler at any time - alowing someone
to go back to a pre-meteform state, and edit something, or say - change
the number of sections on a primitive made over 50 edits ago. Although
this could currently be done with a series of undo's and redo's, the
buffers would be huge. We could store all edits in an ascii file, and
make a small interface that would alow you to go back and edit any of
those commands easily. Then each edited stack could also be saved for
stack undo's. The files would be fairly small, because only the
information in the numeric requesters, and the tool being used (and
layer) would be recorded. Will this be possable with the plug-in
implimentation as it stands? If not could you add this ability? It would
be an awsome feature.. :) And it seems like it would be fairly easy for
us to program. (Joe Angell & Jason Booth).

AND PUT IN A KEY FOR WELD!!! Thanks. :)

   and how 'bout a cylidrical map rotaion setting? Alright - I'll shut up
now.. :)


-- Joe
  --  Jason

--
Joe Angell <[e-mail]> sent this message.
To Post a Message           : [e-mail]
Un/Subscription Requests To : [e-mail]
(DIGEST)                 or : [e-mail]
Administrative Items To     : [e-mail]